-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend issue template yaml engine #29274
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at this more, I wanted to clarify, is this intended to be settable for all types or just checkboxes?
The docs changes seem to imply all, as does the description, but a lot of the code seems to be only checking for checkboxes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes I proposed can still be added later on, so here's my approval to get it into 1.22.
@delvh addressed your issues :) |
feel free to create an issue and assign me if the wording or something else need a followup then :) |
* upstream/main: Replace some `gt-` classes with `tw-` (go-gitea#29570) Enable/disable owner and repo projects independently (go-gitea#28805) Add an trailing slash to dashboard links (go-gitea#29555) Extend issue template yaml engine (go-gitea#29274) [skip ci] Updated licenses and gitignores Fix workflow trigger event IssueChangeXXX bug (go-gitea#29559) Fix 500 when pushing release to an empty repo (go-gitea#29554) Update js and py dependencies, bump python (go-gitea#29561) Filter Repositories by type (go-gitea#29231)
Add new option:
visible
: witch can hide a specific field of the form or the created content afterwardsIt is a string array witch can contain
form
andcontent
. If onlyform
is present, it wont show up in the created issue afterwards and the other way around. By default it sets both except for markdownAs they are optional and github don't have any similar thing, it is non breaking and also do not conflict with it.
With this you can:
Demo
Demo Video
Sponsored by Kithara Software GmbH